Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0444

reference: 191-tree-1
name: 0444
tree-preservation-order: undefined
191-tpo-1
uprn
address-text
point: POINT (-0.940749 50.862070)
geometry: MULTIPOLYGON (((-0.940693 50.862064,-0.940695 50.862075,-0.940703 50.862085,-0.940715 50.862093,-0.940731 50.862098,-0.940749 50.862100,-0.940766 50.862099,-0.940782 50.862094,-0.940795 50.862086,-0.940803 50.862076,-0.940806 50.862065,-0.940804 50.862054,-0.940796 50.862044,-0.940783 50.862036,-0.940768 50.862030,-0.940750 50.862028,-0.940733 50.862030,-0.940717 50.862035,-0.940704 50.862043,-0.940696 50.862053,-0.940693 50.862064)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL